Surveys And Feedback Forms

As engineering managers, we’re constantly striving to build better products, improve team performance, and foster a healthy engineering culture. But how often do we systematically solicit the input needed to make truly informed decisions? Too often, we operate on assumptions or react to vocal minorities, leaving valuable insights untapped. That’s where thoughtfully designed surveys and feedback forms come in. I once saved a project from derailing simply by asking a quick pulse survey that revealed a critical, unspoken dependency. This experience cemented my belief in the power of proactive feedback.

This isn’t about just collecting data; it’s about leveraging feedback as a core stakeholder management tool to drive positive change. Let’s dive into how to do it right.

Why Surveys Matter for Engineering Managers

Here’s how strategically used surveys benefit us:

• Proactive Problem Identification: Instead of waiting for issues to surface in retrospectives or 1:1s, proactively identify pain points in processes, tools, or communication.
• Gauge Team Sentiment: Understand morale, engagement, and identify potential burnout before it impacts productivity – for example, noticing a consistent drop in ‘energy’ scores in weekly pulse surveys.
• Inform Technical Decisions: Get input from the team on architecture choices, tech stack decisions, or prioritization of technical debt. (This builds buy-in and leverages collective expertise!)
• Validate Assumptions: Challenge your own biases and understand how your team actually perceives a situation, not how you think they do.
• Stakeholder Alignment: Ensure alignment with other teams by gathering feedback on how their dependencies impact the engineering team's work, and vice versa. This fosters collaboration and prevents misunderstandings.

Types of Surveys for Engineering Managers

Not all feedback is created equal. Here's a breakdown of the most useful types for us:

Survey Type	Frequency	When to Use
Pulse Surveys	Weekly or Bi-Weekly	Check in on specific areas like morale, project health, or recent changes.
Project Retrospectives	After Project Milestone	Identify what went well, what didn't, and what to improve.
Process Improvement Surveys	As Needed	Gather feedback on specific processes (e.g., code review, on-call rotation, deployment pipeline).
Engagement Surveys	Annually/Semi-Annually	Measure overall team engagement, satisfaction, and identify areas for improvement in company culture.
360° Feedback	Annually/Bi-Annually	Gather feedback from peers, direct reports, and managers for individual development.

A Word of Caution on 360° Feedback: While powerful, 360° feedback can be problematic if not implemented carefully. Potential issues include bias, fear of retribution, and a lack of actionable insights. Start with a small pilot group, ensure anonymity is rigorously maintained, and focus on developmental goals rather than performance evaluations.

Designing Effective Surveys: Avoid the Pitfalls

This is where many surveys fail. Here’s how to avoid common mistakes:

• Keep it Concise: Respect your team’s time. Shorter surveys have higher completion rates. Focus on 3-5 key questions per pulse survey and keep comprehensive surveys under 15-20 questions.
• Use Clear, Unambiguous Language: Avoid jargon, technical terms, or leading questions. Instead of "Do you find our new CI/CD pipeline efficient?", ask "How satisfied are you with the current CI/CD pipeline?" Here's a comparison:
  • Bad: "Is the new deployment process streamlined?"
  • Good: "How easy or difficult is it to deploy changes using the new process?"
• Mix Question Types: Utilize a combination of multiple-choice, rating scales (Likert scales are great), and open-ended questions. Open-ended questions provide valuable qualitative data.
• Ensure Anonymity (Where Appropriate): For sensitive topics (e.g., morale, manager feedback), ensure respondents feel safe providing honest feedback. Tools typically allow for anonymous submissions. Crucially, actually ensure anonymity. Team members will quickly lose trust if they suspect their responses are identifiable.
• Test Before You Launch: Pilot your survey with a small group before distributing it to the entire team to identify confusing questions or technical issues.
• Close the Loop – Crucially Important! Don’t just collect data and let it sit. Share the results with the team (aggregated, anonymized where appropriate), and clearly articulate what actions will be taken based on the feedback. This demonstrates you value their input and builds trust.

Tools to Help

There are a lot of survey tools available. Here's a quick overview:

• Vidhook, Survicate: Good options for delightful, high-response surveys, but may be limited in customization.
• SurveyMonkey: A solid, well-established option with a generous free tier and a wide range of templates.
• Qualtrics Survey: A more robust (and potentially complex) tool, ideal for complex surveys and professional reporting. However, it has a steeper learning curve.
• feedback.fish: Good for quick, free feedback collection, but limited to 25 submissions.

Choose the tool that best fits your needs and budget. A simple table comparing features, price and ease of use can be helpful in your decision.

A Simple Framework: The "What, So What, Now What?"

When analyzing survey results, I use a simple framework to ensure actionability:

• What: What did we learn from the survey? (Identify key themes and trends.)
• So What: Why does this matter? (Connect the findings to business outcomes, team performance, or engineering culture.)
• Now What: What specific actions will we take based on this feedback? (Assign owners and deadlines for each action.)

Here’s an example:

What	So What	Now What
70% of team reported difficulty with the new code review tool	This slows down development velocity and introduces potential bugs	Schedule training sessions on the tool and explore alternative options.

A simple 3-column table outlining "What, So What, Now What" is a highly effective way to present and track survey findings.

Final Thoughts

Surveys aren't just about collecting data; they're about building a culture of continuous improvement and valuing your team’s voice. By approaching surveys strategically, designing them thoughtfully, and – most importantly – acting on the feedback, you can unlock a wealth of insights and empower your team to build not just better products, but a better engineering culture. By embracing a culture of continuous feedback, you can empower your team to build not just better products, but a better engineering culture.